Auto-Fix Summary

0 issues fixed, 0 skipped across 6 files

Ask @claude on this PR if you'd like an explanation of any fix.

Auto-Fix Summary

0 issues fixed, 0 skipped across 6 files

Ask @claude on this PR if you'd like an explanation of any fix.

Auto-Fix Summary

0 issues fixed, 0 skipped across 6 files

Ask @claude on this PR if you'd like an explanation of any fix.

Code Review

No correctness, security, build, or routing issues found.

This PR is almost entirely training/documentation content (estimated-length updates, "1Secure" → "1Secure Pro" renames, link text). The only structural change is the new NAA26Reports training course, which is wired correctly:

• New file src/training/access-analyzer-26/3021.md follows the same structure as its sibling 3020.md (imports NAA, ## heading, body, estimated length).
• src/training/access-analyzer-26/index.js adds export { default as NAA26Reports } from './3021.md'; — the referenced file exists, so no missing-module build break.
• Both consumers (docs/customer/training/product/access-analyzer-data.md and docs/partner/presales/access-analyzer-26.md) update their import { ... NAA26Reports ... } statements to match the new export, and render <NAA26Reports /> in the body.

No changes to products.js, docusaurus.config.js, sidebars, the KB copy pipeline, or any GitHub Actions workflow. Nothing that affects the build or routing.

(Note: I did not assess the doc content/style or whether the updated estimated-length totals add up — a separate workflow handles that.)

Documentation PR Review

Editorial Review

docs/customer/training/learn-about/1secure.md

• No issues found. (Estimated-length value update only.)

docs/customer/training/product/1secure.md

• No issues found. (Estimated-length value update only.)

docs/customer/training/product/access-analyzer-data.md

• No issues found. The new 3021 Netwrix Access Analyzer 26 – Reports & Data Security course is added at the end of the course list and the <NAA26Reports /> component is placed after <NAA26Intro />, matching the listed order. Placement and completeness are correct.

docs/partner/presales/1secure.md

• Clarity — Lines 1, 6: The title and description were renamed to "Netwrix 1Secure Pro", but the body still renders "Netwrix 1Secure" everywhere through the <N1S /> component (defined in src/training/products/1secure.md, which outputs Netwrix 1Secure). A reader sees "Pro" in the title and heading but "Netwrix 1Secure" in every course name and the intro sentence. Confirm whether the product name change to "Pro" should also be reflected in the <N1S /> component and course titles, or whether the title should stay "Netwrix 1Secure" for consistency. Note that the customer-facing learning paths (docs/customer/training/product/1secure.md and docs/customer/training/learn-about/1secure.md) were not renamed, so the doc set is currently split between "1Secure" and "1Secure Pro".

docs/partner/presales/access-analyzer-26.md

• No issues found. The 3021 Netwrix Access Analyzer 26 – Reports & Data Security course is inserted between 3020 Introduction and 5020 Demo in the list, and the <NAA26Reports /> component is placed in the matching position between <NAA26Intro /> and <NAA26Demo />. Order is consistent.

docs/partner/presales/index.md

• No issues found. All "Netwrix 1Secure Presales Engineer" link labels were renamed to "Netwrix 1Secure Pro Presales Engineer" consistently across every category, and the link targets (./1secure.md) are unchanged. See the consistency note on docs/partner/presales/1secure.md regarding the product name itself.

Summary

1 editorial suggestion across 6 files. The bulk of this PR is mechanical (estimated-length updates, a new course component, and a consistent link-label rename) and reads cleanly. The one item worth a writer's attention is the "1Secure" vs "1Secure Pro" naming split between the presales page title and its component-rendered body. Vale and Dale issues are auto-fixed separately.

What to do next:

Comment @claude on this PR followed by your instructions to get help:

• @claude fix all issues — fix all editorial issues
• @claude help improve the flow of this document — get writing assistance
• @claude explain the voice issues — understand why something was flagged

You can ask Claude anything about the review or about Netwrix writing standards.

Automated fixes are only available for branches in this repository, not forks.